Skip to content

[FIX] Allow to deactivate and restore quick creation without restarting - #300

Closed
StefanRijnhart wants to merge 2 commits into
OCA:8.0from
StefanRijnhart:8.0-quick_create_no_restart
Closed

[FIX] Allow to deactivate and restore quick creation without restarting#300
StefanRijnhart wants to merge 2 commits into
OCA:8.0from
StefanRijnhart:8.0-quick_create_no_restart

Conversation

@StefanRijnhart

Copy link
Copy Markdown
Member

The implementation marks seen model objects with a special attribute to prevent unnecessary processing. If a model was modified, _register_hook was called but the attribute prevented quick creation to be disabled. Also, re-enabling quick creation at run time was not supported.

Comment thread base_optional_quick_create/model.py Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pedrobaeza

Copy link
Copy Markdown
Member

Why don't expand https://github.com/OCA/web/tree/8.0/web_m2x_options? In my opinion, this is more a web client issue than a base/server one. You can take the idea of creating ir.parameter per model like in this module: https://github.com/OCA/social/blame/9.0/mail_restrict_follower_selection/README.rst#L13

@StefanRijnhart

StefanRijnhart commented Nov 26, 2015 via email

Copy link
Copy Markdown
Member Author

@pedrobaeza

Copy link
Copy Markdown
Member

Yeah, I know, but I'm talking about implementing this granularity in that module, and make it at web client level, where it should be (as is this web client who includes the quick create option, not the ORM). Obviously, this requires to be done in JS.

@pedrobaeza

Copy link
Copy Markdown
Member

I didn't see that this module already exists, but for me it is a mistake to be implemented this way.

@StefanRijnhart StefanRijnhart added this to the 8.0 milestone Nov 26, 2015
@StefanRijnhart

Copy link
Copy Markdown
Member Author

@pedrobaeza maybe you are right but can we keep this module in its current form in the 8.0 branch for the sake of continuity?

@pedrobaeza

Copy link
Copy Markdown
Member

OK, but please put a warning about this in the Known issues for the v9 migration.

@StefanRijnhart StefanRijnhart self-assigned this Feb 13, 2016
@eLBati

eLBati commented Mar 2, 2016

Copy link
Copy Markdown
Member

@StefanRijnhart as #352 is merged, what is the destiny of this?

[RFR] Don't keep our own check attribute, use the patch mechanism's 'origin' attribute instead
[RFR] Only pass models to the patch method that need patching
@StefanRijnhart

Copy link
Copy Markdown
Member Author

@eLBati I have rebased

@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.09%) to 55.826% when pulling 2c7ca24 on StefanRijnhart:8.0-quick_create_no_restart into 6e097c5 on OCA:8.0.

@sbidoul

sbidoul commented Apr 19, 2016

Copy link
Copy Markdown
Member

👍

Can we merge this in 8.0 at least?

@eLBati

eLBati commented Jul 14, 2016

Copy link
Copy Markdown
Member

👍 thanks

@github-actions

github-actions Bot commented Nov 7, 2021

Copy link
Copy Markdown

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions Bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Nov 7, 2021
SiesslPhillip pushed a commit to grueneerde/OCA-server-tools that referenced this pull request Nov 20, 2024
Syncing from upstream OCA/server-tools (10.0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs review stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants